Usage data index for wireless communication networks

ABSTRACT

In a wireless communication network, index circuitry transfers a reference Distributed Ledger (DL) request to reference circuitry. The reference circuitry transfers a response indicating a reference DL ID to the index circuitry. The index circuitry transfers the reference DL ID to the wireless communication network. The reference circuitry receives usage data and the reference DL ID from the wireless communication network. The reference circuitry stores the usage data in reference DL blocks, generates a usage abstraction of the usage data, and transfers the reference DL ID and the usage abstraction to the index circuitry. The index circuitry stores the usage abstraction and the reference DL ID in index DL blocks. The index circuitry receives requests having the reference DL ID and returns the usage abstraction. The reference circuitry receives requests having the reference DL ID and usage abstraction ID and returns the usage data.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services include voicecalling, Internet access, media streaming, machine communications,vehicle control, and social networking. Exemplary wireless user devicescomprise phones, computers, vehicles, robots, sensors, and drones. Thewireless communication networks have wireless access nodes that exchangewireless signals with the wireless user devices using wireless networkprotocols. Exemplary wireless network protocols include Institute ofElectrical and Electronic Engineers (IEEE) 802.11 (WIFI), Long TermEvolution (LTE), Fifth Generation New Radio (5GNR), and NarrowbandInternet of Things (NB IoT).

The wireless protocols transport user data and network signaling. Todeliver the wireless data services, the wireless access nodes oftenexchange user data and network signaling with wireless network cores.The wireless network cores host network controllers and gateways. Thenetwork controllers exchange network signaling with the wireless userdevices, access nodes, and gateways to direct the delivery of thewireless data services. The wireless access nodes and gateways exchangeuser data to deliver the wireless data services.

Some of the network controllers and gateways track the delivery of thewireless data services to the wireless user devices. The gatewaysgenerate usage data that characterizes their handling of the user databy device, time, location, service, and the like. A common example ofusage data is a Call Detail Record (CDR) that is generated by LTEnetworks. The wireless communication networks transfer the usage data toan accounting computer system that classifies and rates the usage data.The classification identifies services, accounts, and the like. Therating processes the classified data to generate billable costs per userservice plans.

A wireless communication network serves home user devices and also billsthe home users for the corresponding service costs. The same wirelesscommunication network also serves roaming user devices that are home toother networks. The roaming network does not bill the users of roamingdevices. Instead, the roaming network transfers usage data for theroaming user devices to their home networks. The home networks bill thentheir own home users for the roaming services. The roaming and homewireless communication networks settle the roaming costs amongthemselves.

Distributed ledgers are used to handle transactional data like accountbalances using a blockchain format. A distributed ledger has multiplegeographically-diverse computer nodes that each have a copy of chaincode and a copy of data blocks. The computer nodes execute the chaincode to test and then build a consensus on the results of chain codeexecution. For example, multiple computer nodes each execute chain codeto determine a user's new balance and then build a consensus on the newbalance before proceeding. Once a consensus is reached, then thecomputer nodes each store a new data block in their own blockchaindatabase. The data block indicates chain code results and has a hash ofthe previous data block. The redundancy, consensus, and hashes make thedistributed ledger highly reliable, secure, and visible.

Distributed ledgers may be used between wireless communication networksto handle usage data for roaming user devices. Unfortunately, the staticnature of chain code and blockchain databases may cause problems. Thechain code may become obsolete as wireless data services change. Thedatabases may overload or slow when wireless data services are heavilyused for extended periods of time. Moreover, the databases may becomehuge and difficult to analyze.

TECHNICAL BACKGROUND

In a wireless communication network, index circuitry transfers areference Distributed Ledger (DL) request to reference circuitry. Thereference circuitry transfers a response indicating a reference DL ID tothe index circuitry. The index circuitry transfers the reference DL IDto the wireless communication network. The reference circuitry receivesusage data and the reference DL ID from the wireless communicationnetwork. The reference circuitry stores the usage data in reference DLblocks, generates a usage abstraction of the usage data, and transfersthe reference DL ID and the usage abstraction to the index circuitry.The index circuitry stores the usage abstraction and the reference DL IDin index DL blocks. The index circuitry receives requests having thereference DL ID and returns the usage abstraction. The referencecircuitry then receives requests having the reference DL ID and theusage abstraction ID and returns the usage data.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates data communication circuitry that indexes usage datafrom a wireless communication network for usage analytics circuitry.

FIG. 2 illustrates the operation of the data communication circuitry toindex the usage data from the wireless communication network for theusage analytics circuitry.

FIG. 3 illustrates the operation of the data communication circuitry toindex the usage data from the wireless communication network for theusage analytics circuitry.

FIG. 4 illustrates the operation of the data communication circuitry toindex the usage data from the wireless communication network for theusage analytics circuitry.

FIG. 5 illustrates a wireless communication network having a NetworkFunction Virtualization Infrastructure (NFVI) that indexes usage datafrom other wireless communication networks for a usage analytics engine.

FIG. 6 illustrates a wireless User Equipment (UE).

FIG. 7 illustrates a wireless Access Point (AP).

FIG. 8 illustrates a data communication system that indexes usage datafor multiple wireless communication networks for a usage analyticsengine.

DETAILED DESCRIPTION

FIG. 1 illustrates data communication circuitry 120 that indexes usagedata from wireless communication network 110 for usage analyticscircuitry 130. Data communication circuitry 120 comprises indexcircuitry 121 and reference circuitry 122. Index circuitry 121 andreference circuitry 122 comprise microprocessors, memory, software,transceivers, and bus connections. The microprocessors comprise CentralProcessing Units (CPUs), Graphical Processing Units (GPUs),Application-Specific Integrated Circuits (ASICs), and/or the like. Thememories comprise Random Access Memory (RAM), flash circuitry, diskdrives, and/or the like. The memories store software like operatingsystems, network applications, and virtual components

Index circuitry 121 comprises index Distributed Ledger (DL) 123. IndexDL 123 comprises index chain code 125, top index block 127, and olderindex blocks that are shown below index block 127. Except for theinitial genesis block, each index block has an index DL ID, reference DLID, usage abstraction (ABST), and a last block hash. Reference circuitry122 comprises reference DL 124. Reference DL 124 comprises referencechain code 126, top reference block 128, and older reference blocks thatare shown below reference block 128. Except for the initial genesisblock, each reference block has an index DL ID, reference DL ID, usagedata, and a last block hash.

UEs 101-103 comprise user circuitry that interacts with users. UEs101-103 also comprise radio circuitry that wirelessly communicates withwireless communication network 110. UEs 101-103 might be phones,computers, robots, sensors, vehicles, drones, data appliances, or someother user apparatus with wireless communication circuitry.

Wireless communication network 110 comprises wireless access points andother network elements like network controllers, gateways, anddatabases. Wireless communication network 110 serves UEs 101-103 withwireless communication services. The wireless access points includeantennas, modulators, amplifiers, filters, digital/analog interfaces,microprocessors, memory, software, transceivers, and bus connections.The other network elements include microprocessors, memory, software,transceivers, and bus connections. The microprocessors comprise DigitalSignal Processors (DSPs), CPUs, GPUs, Field Programmable Gate Arrays(FPGAs), ASICs, and/or the like. The memories comprise RAM, flashcircuitry, disk drives, and/or the like. The memories store softwarelike operating systems, network applications, and virtual components.

Usage analytics circuitry 130 comprises microprocessors, memory,software, transceivers, and bus connections. The microprocessorscomprise CPUs, GPUs, ASICs, and/or the like. The memories comprise RAM,flash circuitry, disk drives, and/or the like. The memories storesoftware like operating systems, analytic applications, and virtualcomponents.

Index circuitry 121 and reference circuitry 122 are coupled to eachother, wireless communication network 110, and usage analytics circuitry130 by network communication links. The network communication links mayuse Institute of Electrical and Electronic Engineers (IEEE) 802.3(Ethernet), Time Division Multiplex (TDM), Data Over Cable SystemInterface Specification (DOCSIS), Internet Protocol (IP), IEEE 802.11(WIFI), Long Term Evolution (LTE), Fifth Generation New Radio (5GNR),Narrowband Internet-of-Things (NB-IoT), or some other data protocol.Wireless communication network 110 and User Equipment (UEs) 101-103 arecoupled over wireless communication links. The wireless links may useWIFI, LTE, 5GNR, NB-IoT, or some other wireless protocol. WIFI, LTE,5GNR, and NB-IoT may use frequencies in the low-band, mid-band,millimeter-wave band, and/or some other part of the wireless spectrum.Ethernet and WIFI are described in IEEE documents. LTE, 5GNR, and NB-IoTare described in Third Generation Partnership Project (3GPP) documents.

In operation, index circuitry 121 receives a usage data request forwireless communication network 110. The usage data request may be fromwireless communication network 110 or from another entity on behalf ofwireless communication network 110. Index circuitry 121 starts index DL123 for wireless communication network 110. Index DL 123 has an ID likea code, name, address, or the like. Responsive to the usage datarequest, index circuitry 121 transfers a reference DL request toreference circuitry 122 to establish reference DL 124 for wirelesscommunication network 110. The reference DL request indicates the indexDL ID.

Reference circuitry 122 receives the reference DL request and startsreference DL 124 for wireless communication network 110. The referenceDL has an ID like a code, name, address, or the like. Referencecircuitry 122 transfers a reference DL response that indicates the indexDL ID and the reference DL ID to index circuitry 121. Index circuitry121 receives the reference DL response and associates the index DL ID,reference DL ID, and wireless communication network 110 with oneanother. Index circuitry 121 transfers a usage data response thatindicates the reference DL ID and the index DL ID for wirelesscommunication network 110. Index circuitry 121 may transfer the usagedata response to wireless communication network 110 or to another entityon behalf of wireless communication network 110.

UEs 101-103 and wireless communication network 110 exchange wirelesssignals that carry user data and network signaling to deliver wirelessdata services to UEs 101-103. The network elements in wirelesscommunication network 110 generate usage data that characterizes theexchange of the wireless signals and the delivery of the wireless dataservices to UEs 101-103 by wireless communication network 110. The usagedata typically indicates UEs 101-103, their data transfer amounts, andthe data transfer times. The usage data may also indicate UE location,data service, data type, and other pertinent information. In someexamples, the usage data comprises Call Detail Records (CDRs). Wirelesscommunication network 110 transfers the usage data along with thereference DL ID and index DL ID to reference circuitry 122.

Reference circuitry 122 receives the reference DL ID, index DL ID, andusage data from wireless communication network 110. In response to thereference DL ID, reference circuitry 122 executes reference DL chaincode 126 for reference DL 124. In response to the code execution,reference circuitry 122 stores the usage data in reference DL blockslike reference block 128. These reference DL blocks include the index DLID, reference DL ID, usage data, and last block hashes. In someexamples, the reference DL chain code classifies and rates the usagedata before storage.

In response to a data amount, time period, or some other abstractiontrigger, reference circuitry 122 generates a usage abstraction of theusage data. Reference chain code 126 performs the abstraction. Theabstraction process may use a mask, compression, translation, redaction,and/or, or some other technique to abstract the usage data. The usageabstractions have usage abstraction IDs and may comprise abstractions ofclassified and rated usage data.

Reference circuitry 122 transfers the index DL ID, reference DL ID, andthe usage abstraction to index circuitry 121. Index circuitry 121receives the usage abstraction, index DL ID, and reference DL ID. Inresponse to the index DL ID, index circuitry 121 executes index DL chaincode 125 for the index DL. In response to the code execution, indexcircuitry 121 stores the usage abstraction a new index DL block likeindex block 127. The new DL index block includes the index DL ID,reference DL ID, usage abstraction, and last block hashes.

Usage analytics circuitry 130 generates an index data request forwireless communication network 110 that includes the index DL ID and thereference DL ID. The index data request may indicate an amount ofrequested usage abstractions. Usage analytics circuitry 130 transfersthe usage data request to index circuitry 121. Index circuitry 121receives the index data request for wireless communication network 110and responsively identifies one or more usage abstractions for the indexDL ID and reference DL ID based on the requested amount. Index circuitry121 transfers the usage abstractions, index DL ID, and reference DL IDto usage analytics circuitry 130.

Usage analytics circuitry 130 receives the usage abstractions, index DLID, and reference DL ID from index circuitry 121. In response, usageanalytics circuitry 130 generates a reference data request for wirelesscommunication network 110 that includes the index DL ID, reference DLID, and some of the usage abstraction IDs. Usage analytics circuitry 130transfers the reference data request to reference circuitry 122.Reference circuitry 122 receives the reference data request andresponsively identifies the usage data for index DL ID, reference DL ID,and selected abstraction IDs. Reference circuitry 122 transfers thecomplete usage data for the selected abstractions to usage analyticscircuitry 130. The usage data may comprise the classified and ratedusage data.

After storing a pre-determined amount of the usage data, the expirationof a time period, and/or some other exhaustion trigger, referencecircuitry 122 transfers a reference DL exhaustion notice to indexcircuitry 122. Index circuitry 122 receives the reference DL exhaustionnotice and transfers another reference DL request to reference circuitry122 to establish another reference DL for wireless communication network110. Reference circuitry 122 receives the other reference DL request andthe above operation repeats for the new reference DL. The exhaustionprocess may be used to switch from one reference DL to another or to addanother reference DL while using the existing DL. For example, theexhaustion process could be used to modify the reference chain code. Theexhaustion process could be used to add new reference chain code for anew wireless data service.

Wireless communication network 110 is divided into geographic areas likesectors, tracking areas, zones, or the like. The usage data indicatesspecific geographic areas where individual UEs 101-103 receive theirwireless data services. Index circuitry 121 and reference circuitry 122may associate the index DL ID, reference DL ID, usage data, and usageabstractions with their specific geographic areas. Thus, circuitry121-122 may serve usage analytics circuitry 130 with indexed usage datafor specific geographic areas. Data communication circuitry 120 mayserve additional wireless communication networks and usage analyticengines in a similar manner.

Advantageously, data communication circuitry 120 indexes distributedledgers that may store huge amounts of usage data. Moreover, datacommunication circuitry 120 effectively avoids database overload andefficiently replaces or supplements the distributed ledgers.

FIG. 2 illustrates the operation of data communication circuitry 120 toindex the usage data from wireless communication network 110 for usageanalytics circuitry 130. Index circuitry 121 receives a usage datarequest from wireless communication network 110 (201). Index circuitry121 starts index Distributed Ledger (DL) 123 for wireless communicationnetwork 110 and transfers a reference DL request to reference circuitry122 to establish reference DL 124 for wireless communication network 110(201).

Reference circuitry 122 receives the reference DL request and startsreference DL 124 for wireless communication network 110 (202). Referencecircuitry 122 transfers a reference DL response that indicates thereference DL ID to index circuitry 121 (202). Index circuitry 121receives the reference DL response and transfers a usage data responsethat indicates the reference DL ID to wireless communication network 110(203). Reference circuitry 122 receives the reference DL ID and usagedata from wireless communication network 110 (204). Reference circuitry122 executes reference DL chain code 126 for reference DL 124 (204).Reference circuitry 122 stores the usage data, reference DL ID, andhashes in reference DL blocks (204). In some examples, the reference DLchain code classifies and rates the usage data and then storesclassified and rated usage data in the reference DL blocks (204).

In response to an abstraction trigger (205), reference circuitry 122generates a usage abstraction of the usage data (206). Referencecircuitry 122 transfers the reference DL ID and usage abstraction toindex circuitry 121 (206). Index circuitry 121 receives reference DL IDand usage abstraction (207). Index circuitry 121 executes index DL chaincode 125 for index DL 123 (207). Index circuitry 121 stores thereference DL ID, usage abstraction, and hash in a new index DL block(207).

Index circuitry 121 receives an index data request for wirelesscommunication network that indicates the reference DL ID (208). Indexcircuitry 121 identifies usage abstractions for the reference DL ID(208). Index circuitry 121 transfers the usage abstractions andreference DL ID to usage analytics circuitry 130 (208). Referencecircuitry 122 receives a reference data request from usage analyticscircuitry 130 that has the reference DL ID and usage abstraction IDs(209). Reference circuitry 122 identifies the usage data for thereference DL ID and abstraction IDs (209). Reference circuitry 122transfers the complete usage data to usage analytics circuitry 130(209). In some examples, the usage data comprises classified and ratedusage data (209).

In response to an exhaustion trigger (205), reference circuitry 122transfers a reference DL exhaustion notice to index circuitry 122 (210).Index circuitry 122 receives the reference DL exhaustion notice andtransfers another reference DL request to reference circuitry 122 toestablish another reference DL for wireless communication network 110(210). Reference circuitry 122 receives the other reference DL requestand the operation repeats (202). A similar process (210) can be used toadd another reference DL for wireless communication network 110 whilestill using reference DL 124.

FIG. 3 illustrates the operation of data communication circuitry 120 toindex the usage data from wireless communication network 110 for usageanalytics circuitry 130. Wireless communication network 110 transfers ausage data request to index circuitry 121. Index circuitry 121 receivesa usage data request and starts index DL 123 that has an index DL ID.Index circuitry 121 also transfers a reference DL request to referencecircuitry 122 to establish reference DL 124 for wireless communicationnetwork 110. The reference DL request indicates the index DL ID.

Reference circuitry 122 receives the reference DL request and startsreference DL 124 having a reference DL ID for wireless communicationnetwork 110. Reference circuitry 122 transfers a reference DL responsethat indicates the index DL ID and reference DL ID to index circuitry121. Index circuitry 121 receives the reference DL response andassociates wireless communication network 110, the index DL ID, and thereference DL ID with one another. Index circuitry 121 transfers a usagedata response that indicates the reference DL ID and the index DL ID towireless communication network 110.

UEs 101-103 use wireless communication network 110 for wireless dataservices. Wireless communication network 110 generates usage data thatcharacterizes the network usage by UEs 101-103. The usage data maycomprise Call Detail Records (CDRs). Wireless communication network 110transfers the usage data along with the reference DL ID and index DL IDto reference circuitry 122.

Reference circuitry 122 receives the reference DL ID, index DL ID, andthe usage data from wireless communication network 110. In response tothe reference DL ID and index DL ID, reference circuitry 122 executesreference DL chain code 126 for the reference DL. In response to thecode execution, reference circuitry 122 stores the usage data inreference DL blocks like reference block 128. These reference DL blocksinclude the reference DL ID, index DL ID, usage data, and hashes of theprevious reference block. In some examples, reference DL chain code 126classifies and rates the usage data.

In response to an abstraction trigger like a data amount or time period,reference circuitry 122 generates a usage abstraction of the usage data.Reference circuitry 122 transfers the index DL ID, reference DL ID, andthe usage abstraction to index circuitry 121. Index circuitry 121receives the usage abstraction, index DL ID, and reference DL ID. Inresponse to the index DL ID, index circuitry 121 executes index DL chaincode 125 for the index DL. In response to the code execution, indexcircuitry 121 stores the usage abstraction a new index DL block likeindex block 127. The new DL index block includes the index DL ID,reference DL ID, usage abstraction, and hash of the previous indexblock.

Usage analytics circuitry 130 generates an index data request forwireless communication network 110 that includes the index DL ID,reference DL ID, and a time period for requested usage abstractions.Usage analytics circuitry 130 transfers the usage data request to indexcircuitry 121. Index circuitry 121 receives the index data request andresponsively identifies one or more usage abstractions for the index DLID, reference DL ID, and time period. Index circuitry 121 transfers theusage abstractions, index DL ID, and reference DL ID to usage analyticscircuitry 130.

Usage analytics circuitry 130 receives the usage abstractions, index DLID, and reference DL ID from index circuitry 121. In response, usageanalytics circuitry 130 selects some of the usage abstractions andgenerates a reference data request that includes the index DL ID,reference DL ID, and usage abstraction IDs from the selected usageabstractions. Usage analytics circuitry 130 transfers the reference datarequest to reference circuitry 122. Reference circuitry 122 receives thereference data request and responsively identifies the usage data forindex DL ID, reference DL ID, and selected abstraction IDs. Referencecircuitry 122 transfers the usage data to usage analytics circuitry 130.The usage data may comprise the classified and rated usage data. Usageanalytics circuitry 130 processes usage abstractions to select andretrieve the desired usage data.

FIG. 4 illustrates the operation of data communication circuitry 120 toindex the usage data from wireless communication network 110 for usageanalytics circuitry 130. UEs 101-103 use wireless communication network110 for wireless data services. Wireless communication network 110generates usage data and transfers the usage data along with thereference DL ID and index DL ID to reference circuitry 122. Referencecircuitry 122 receives the reference DL ID, index DL ID, and the usagedata from wireless communication network 110. In response to thereference DL ID and index DL ID, reference circuitry 122 executesreference DL chain code 126 for reference DL 124. In response to thecode execution, reference circuitry 122 stores the usage data inreference DL blocks.

Reference circuitry 122 detects exhaustion for reference DL 124. Inresponse to an abstraction trigger, reference circuitry 122 generates ausage abstraction of the usage data. Reference circuitry 122 transfersthe index DL ID, reference DL ID, the usage abstraction, and exhaustionnotice to index circuitry 121. Index circuitry 121 receives the index DLID, reference DL ID, usage abstraction, and exhaustion notice. Inresponse to the index DL ID, index circuitry 121 executes index DL chaincode 125 for index DL 123. In response to the code execution, indexcircuitry 121 stores the usage abstraction a new index DL block.

In response to the exhaustion notice, index circuitry 121 transfers areference DL request to reference circuitry 122 to establish a newreference DL for wireless communication network 110. Reference circuitry122 receives the reference DL request and starts a new reference DLhaving a new reference DL ID and new reference chain code. Referencecircuitry 122 transfers a reference DL response that indicates the indexDL ID and new reference DL ID to index circuitry 121. Index circuitry121 receives the reference DL response and associates wirelesscommunication network 110, the index DL ID, and the new reference DL IDwith one another. Index circuitry 121 transfers a usage data responsethat indicates the new reference DL ID and the index DL ID to wirelesscommunication network 110.

UEs 101-103 use wireless communication network 110 for wireless dataservices. Wireless communication network 110 generates and transfers theusage data, index DL ID, and new reference DL ID and to referencecircuitry 122. Reference circuitry 122 receives the new reference DL ID,index DL ID, and the usage data from wireless communication network 110.In response to the new reference DL ID and index DL ID, referencecircuitry 122 executes the new reference DL chain code for the newreference DL. In response to the code execution, reference circuitry 122stores the usage data in new reference DL blocks. The process thenrepeats and reference circuitry 122 stores more usage data, transfersmore usage abstractions and exhaustion notices, and serves usageanalytics circuitry 130 with usage data.

The exhaustion process may be used to switch from one reference DL toanother or to add another reference DL while still using the existingDL. For example, the exhaustion process could be used to modify thereference chain code by replacing reference DLs and their chain code.The exhaustion process could be used to add new reference DLs with newreference chain code for new wireless data services while continuing touse older reference DLs.

FIG. 5 illustrates wireless communication network 500 having NetworkFunction Virtualization Infrastructures (NFVIs) 521 that index usagedata from wireless communication network 510 for usage analytics engine530. NFVIs 521 are an example of data communication circuitry 120,although circuitry 120 may differ. Wireless communication network 500comprises UEs 501, APs 511, NFVIs 521, and usage analytic engine 530.Wireless communication network 510 comprises UEs 502, APs 512, and NFVIs522. UEs 502, APs 512, and NFVIs 522 are configured and operate like UEs501, APs 511, and NFVIs 521.

NFVIs 521 comprise NFVI hardware, hardware drivers, operating systemsand hypervisors, NFVI virtual layers, and Virtual Network Functions(VNFs). The NFVI hardware comprises Network Interface Cards (NICs),CPUs, RAM, disk storage, and data switches (SW). The virtual layerscomprise virtual NICs (vNIC), virtual CPUs (vCPU), virtual RAM (vRAM),virtual Disk Storage (vDISK), and virtual Switches (vSW). The NICs ofNFVIs 521 are coupled to one another over data communication links.

The VNFs in NFVIs 521 comprise a Distributed Ledger (DL) client, indexDL, and reference (REF) DLs. The VNFs also comprise Authentication andSecurity Function (AUSF), Policy Control Function (PCF), Access andMobility Management Function (AMF), Network Slice Selection Function(NSSF), Session Management Function (SMF), User Plane Function (UPF),and other Fifth Generation Core (5GC) network functions which areomitted for clarity. The NFVI hardware in NFVIs 521 executes thehardware drivers, operating systems, hypervisors, virtual layers, andVNFs to serve UEs 501 over APs 511. In a like manner, NFVIs 522 executetheir hardware drivers, operating systems, hypervisors, virtual layers,and VNFs to serve UEs 502 over APs 512.

In NFVIs 521, the DL client transfers a usage data request for wirelesscommunication network 510 to the index DL which has an index DL ID. Theindex DL transfers a reference DL request for wireless communicationnetwork 510 to a reference DL which has a reference DL ID. The referenceDL associates wireless communication network 510 with the index DL IDand the reference DL ID. The reference DL transfers a reference DLresponse to the index DL that indicates the reference DL ID. The indexDL associates wireless communication network 510 with the index DL IDand the reference DL ID. The index DL transfers a usage data response tothe DL client that indicates the reference DL ID for wirelesscommunication network 510. The DL client transfers the reference DL IDto NFVIs 522 for delivery to the accounting servers that receive usagedata from the UPFs that serve UEs 501.

As indicated by the arrow, UEs 501 move from wireless communicationnetwork 500 to wireless communication network 510—although physicalmobility is not required. After the network move, NFVIs 522 serve UEs501 over APs 512. In NFVIs 522, the VNFs (typically UPFs and accountingservers) generate Call Detail Records (CDRs) or other usage data thatcharacterizes the delivery of wireless data services to UEs 501. TheVNFs in NFVIs 522 transfer the CDRs for UEs 501 and the reference DL IDto the DL client in NFVIs 521. The DL client in NFVIs 521 transfers theCDRs and the reference DL ID to the corresponding reference DL.

The reference DL receives the CDRs and the reference DL ID from the DLclient. The reference DL executes its chain code to classify the CDRs.CDR classification entails the determination of a network service andplan. The reference DL executes its chain code to rate the classifiedCDRs. CDR rating entails determining a monetary cost based on theclassification and metrics like duration/amount, location, andtime/date. The reference DL executes its chain code to store the ratedCDRs in one or more reference DL blocks. The typical reference DL blockincludes the reference DL ID, index DL ID, one or more CDRs,classification/rating metadata, and a hash of the previous referenceblock.

After a pre-determined number of CDRs are received since the last CDRabstraction or after a pre-determined time-period, the reference DLchain code abstracts the rated CDRs. The chain code may use a CDR maskto select data for the abstraction. The chain code determines anabstraction ID and associates the abstraction ID with the abstractedCDRs. The reference DL transfers the CDR abstraction and abstraction IDto the index DL. The index DL executes its index chain code to store theCDR abstraction in an index DL block. The typical index DL blockincludes the index DL ID, reference DL ID, abstraction ID, CDRabstraction, and a hash of the previous index block.

Over time, the reference DL may store large amounts of rated CDRs, andthe index DL may store a smaller amount of CDR abstractions. Afterstoring a pre-determined amount of the CDRs or the expiration of a timeperiod, the reference DL transfers an exhaustion notice to the index DL.The index DL receives the exhaustion notice and transfers anotherreference DL request to another one of the reference DLs for wirelesscommunication network 510. The operation then repeats with the newreference DL. Over time, several reference DLs may store huge amounts ofrated CDRs, and the index DL may store a more moderate amount of CDRabstractions.

To add additional reference DLs that operate in parallel for wirelesscommunication network 510, the DL client transfers additional usage datarequests to the index DL. The DL client then sends the resultingreference DL IDs to NFVIs 522. When multiple reference DLs are used, theDL client adds service data or some other codes so NFVIs 522 canproperly label the CDRs with the correct service data/codes. The sameCDR may be sent to multiple reference DLs. In addition, wirelesscommunication network 510 is divided into geographic areas. The CDRsindicate the specific geographic areas where UEs 501 receive theirwireless data services. The CDR abstractions may also indicate thesespecific geographic areas. In NFVIs 522, the DL client transfers theindex DL IDs, the reference DL IDs, and any service data or other codesto usage analytics engine 530.

Consider an example where wireless communication network 500 has limitedFifth Generation New Radio (5GNR) resources in a geographic area that isserved by wireless communication network 510. Usage analytics engine 530is configured to operate as follows. Usage analytics engine 530generates a CDR abstraction request for the index DL of wirelesscommunication network 510. The CDR abstraction request includes thereference DL ID and a timeframe. Usage analytics engine 530 transfersthe CDR abstraction request to the index DL. The index DL receives therequest and retrieves the CDR abstractions for the reference DL ID andtimeframe. The index DL transfers the CDR abstractions to usageanalytics circuitry 130.

Usage analytics circuitry 130 processes the CDR abstractions to detectspikes in service costs for UEs 501 in particular geographic areas ofwireless communication network 510. In response to a cost spike, usageanalytics engine 530 generates a CDR request for the reference DL andCDR abstraction IDs. Usage analytics engine 530 transfers the CDRrequest to the reference DL. The reference DL retrieves the CDRs for thereference DL ID and CDR abstraction IDs. The reference DL transfers thecomplete CDRs to usage analytics circuitry 530. Usage analyticscircuitry 530 processes the CDRs for the geographic area to detect asurge in 5GNR usage by UEs 501 which caused the cost spike. In responseto the surge in 5GNR usage by UEs 501 in the specific geographic area,wireless communication network 500 may deploy more 5GNR resources tothat geographic area on a priority basis.

FIG. 6 illustrates wireless User Equipment (UE) 501. UE 501 is anexample of UEs 101-103, although these UEs may differ. UE 501 comprisesFifth Generation New Radio (5GNR) circuitry 611, CPU, memory, and userinterfaces which are interconnected over bus circuitry. 5GNR circuitry611 comprises antennas, amplifiers, filters, modulation,analog-to-digital interfaces, DSP, and memory that are coupled over buscircuitry. The antennas in UE 501 are coupled to APs 511-512 overwireless 5GNR links. The user interfaces comprise graphic displays,machine controllers, sensors, cameras, transceivers, and/or some otheruser components. The memories store operating systems, userapplications, and network applications. The network applicationscomprise Physical Layer (PHY), Media Access Control (MAC), Radio LinkControl (RLC), Packet Data Convergence Protocol (PDCP), Radio ResourceControl (RRC), and Service Data Adaptation Protocol (SDAP).

The CPU executes the operating systems, user applications, and networkapplications to exchange network signaling and user data with APs511-512 over 5GNR circuitry 611 and the 5GNR links. In UE 601, the CPUreceives Uplink (UL) user data and signaling from the user applicationsand transfers user data and signaling to memory. The CPU executes the5GNR network applications to process the UL user data and signaling andDownlink (DL) 5GNR signaling to generate UL 5GNR symbols that carry 5GNRdata and RRC/N1 signaling. In 5GNR circuitry 611, the DSP processes theUL 5GNR symbols to generate corresponding digital signals for theanalog-to-digital interfaces.

The analog-to-digital interfaces convert the digital UL signals intoanalog UL signals for modulation. Modulation up-converts the UL signalsto their carrier frequencies. The amplifiers boost the modulated ULsignals for the filters which attenuate unwanted out-of-band energy. Thefilters transfer the filtered UL signals through duplexers to theantennas. The electrical UL signals drive the antennas to emitcorresponding wireless 5GNR signals that transport the UL RRC/N1signaling and 5GNR data to APs 511-512.

In 5GNR circuitry 611, the antennas receive wireless signals from APs511-512 that transport Downlink (DL) RRC/N1 signaling and 5GNR data. Theantennas transfer corresponding electrical DL signals through duplexersto the amplifiers. The amplifiers boost the received DL signals forfilters which attenuate unwanted energy. In modulation, demodulatorsdown-convert the DL signals from their carrier frequencies. Theanalog/digital interfaces convert the analog DL signals into digital DLsignals for the DSP. The DSP recovers DL 5GNR symbols from the DLdigital signals. The DSP transfer the DL 5GNR symbols to memory. TheCPUs execute the 5GNR network applications to process the DL 5GNRsymbols and recover the DL RRC/N1 signaling and 5GNR data. The CPUstransfer corresponding user data and signaling to the user applications.The user applications process the DL user data and signaling to interactwith the user interfaces.

In some examples, the RRC, SDAP, or a user application in UE 501 mayreceive usage reporting instructions having the reference DL ID, and inresponse, transfer usage data having the reference DL ID to the DLclient in NFVIs 521 for handling by a reference DL and an index DL.

FIG. 7 illustrates wireless Access Point (AP) 511. AP 511 is an exampleof the APs in wireless communication network 110, although these APs maydiffer. AP 511 comprises Distributed Unit (DU) circuitry 711 andCentralized Unit (CU) circuitry 712. DU circuitry 711 comprises 5GNRcircuitry 721, CPUs, memory, and transceivers (DU XCVR) that are coupledover bus circuitry. 5GNR circuitry 721 comprises antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, and memory thatare coupled over bus circuitry. CU circuitry 712 comprises CPU, memory,and transceivers that are coupled over bus circuitry.

UE 501 is wirelessly coupled to the antennas in 5GNR circuitry 721 overthe wireless 5GNR links. The DU transceivers in DU circuitry 721 arecoupled to the CU transceivers in CU circuitry 712 over network datalinks. The network transceivers in CU circuitry 712 are coupled to NFVIs521 over N2 links and N3 links.

In DU circuitry 711, the memories store operating systems and networkapplications. The network applications include at least some of: PHY,MAC, RLC, PDCP, RRC, and SDAP. In CU circuitry 712, the memories storeoperating systems, virtual components, and network applications. Thevirtual components comprise hypervisor modules, virtual switches,virtual machines, and/or the like. The network applications comprise atleast some of: PHY, MAC, RLC, PDCP, RRC, and SDAP.

The CPU in CU circuitry 712 executes some or all of the 5GNR networkapplications to drive the exchange of 5GNR data and signaling between UE501 and NFVIs 521. The CPU in DU circuitry 711 executes some or all ofthe 5GNR network applications to drive the exchange of 5GNR data andsignaling between UE 501 and NFVIs 521. The functionality split of the5GNR network applications between DU circuitry 711 and CU circuitry 712may vary. CU circuitry 712 may hosts VNFs in the same manner as NFVIs521.

In 5GNR circuitry 721, the antennas receive wireless signals from UE 501that transport UL 5GNR data and RRC/N1 signaling. The antennas transfercorresponding electrical UL signals through duplexers to the amplifiers.The amplifiers boost the received UL signals for filters which attenuateunwanted energy. In modulation, demodulators down-convert the UL signalsfrom their carrier frequencies. The analog/digital interfaces convertthe analog UL signals into digital UL signals for the DSP. The DSPrecovers UL 5GNR symbols from the UL digital signals. In DU circuitry711 and/or CU circuitry 712, the CPUs execute the 5GNR networkapplications to process the UL 5GNR symbols to recover the UL RRC/N1signaling and 5GNR data. The network applications process the UL RRC/N1signaling, UL 5GNR data, DL N2/N1 signaling, and DL N3 data to generateDL RRC/N1 signaling, DL 5GNR data, UL N2/N1 signaling, and UL N3 data.In CU circuitry 712, the network transceivers transfer the UL N2/N1signaling and UL N3 data to NFVIs 521 over the N2 and N3 links.

In CU circuitry 712, the network transceivers receive the DL N2/N1signaling and DL N3 data from NFVIs 521 over the N2 and N3 links. In DUcircuitry 711 and/or CU circuitry 712, the CPUs execute the 5GNR networkapplications to process the DL N2/N1 signaling and N3 data to generatethe DL RRC/N1 signaling and the DL 5GNR data. The network applicationsprocess the DL RRC/N1 signaling and DL 5GNR data to generate DL 5GNRsymbols. In DU circuitry 711, the DSP processes the DL 5GNR symbols togenerate corresponding digital signals for the analog-to-digitalinterfaces. The analog-to-digital interfaces convert the digital DLsignals into analog DL signals for modulation. Modulation up-convertsthe DL signals to their carrier frequencies. The amplifiers boost themodulated DL signals for the filters which attenuate unwantedout-of-band energy. The filters transfer the filtered DL signals throughduplexers to the antennas. The electrical DL signals drive the antennasto emit corresponding wireless 5GNR signals that transport the DL RRC/N1signaling and 5GNR data to UE 501 over the 5GNR links.

In some examples, the RRC, SDAP, or VNF in CU circuitry 712 of AP 511may receive usage reporting instructions having the reference DL ID, andin response, transfer usage data having the reference DL ID to the DLclient in NFVIs 521 for handling by a reference DL and an index DL.

FIG. 8 illustrates data communication system 820 that indexes usage datafrom multiple wireless communication networks 800 for usage analyticsengine 830. Wireless communication networks 800 are an example ofwireless communication network 110, although network 110 may differ.Data communication system 820 is an example of data communication system120, although system 120 may differ. Wireless communication networks 800comprise UE 801 AP 811, and NFVI 812. Wireless communication networks800 have many other UEs, APs, and NFVIs. Data communication system 820comprises index DL 821, reference DL 822, and DL controller 823. IndexDL 821 comprises an endorser node, orderer node, peer node, index DLcode, and DL database (DB). Reference DL 822 comprises an endorser node,orderer node, peer node, reference DL code, and DL database. The otherindex DLs and reference DLs have endorser nodes, orderer nodes, peernodes, DL code, and DL databases.

NFVI 812 executes the client which transfers a data request to DLcontroller 823 in data communication system 820. DL controller 823responsively initiates index DL 821 and transfers a correspondingrequest to an endorser node in index DL 821. The endorser node executesthe index DL code in index DL 821 to process the request and selectreference DL 822 for the client in NFVI 812. The endorser node checksthe code results against an endorsement rule set that has requirements,restrictions, and syntax which the code results must pass beforeendorsement. When the code result passes the endorsement rules, theendorser node transfers a transaction endorsement back to DL controller823.

DL controller 823 transfers the endorsed transaction to an orderer nodein index DL 821. The orderer node transfers the endorsed transaction tothe peer nodes. The peer nodes independently execute the index DL codeto re-process the data request and select reference DL 822 for client inNFVI 812. The peer nodes share their code result (reference DL 822 forthe client in NFVI 812 and other pertinent data). The peer nodes thathave the same code result join a consensus for that result. When aconsensus of peer nodes is formed (like 50%), then the peer nodes storethe consensus result in the DL databases (DBs) using a blockchainformat. The blockchain format stores data in blocks that include a hashof the previous block to form the blockchain. A peer module initiatesreference DL 822 and transfers the ID for reference DL 822 to DLcontroller 823. DL controller 823 transfers the ID for reference DL 822to the client in NFVI 812.

The RRC in UE 801 and the RRC in AP 811 exchange 5GNR RRC/N1 signalingover their respective PDCPs, RLCs, MACs, and PHYs. The RRC in AP 811 andthe AMF in NFVI 812 exchange corresponding 5GNR N2/N1 signaling. The AMFinteracts with UE 801 over N1 and with other VNFs like AUSF and UDM toperform UE authentication and security. The AMF interacts with UE 801over N1 and with other VNFs like PCF and SMF to perform serviceselection. The AMF and SMF select bearers and QoS for the selectedservice. In response to bearer and QoS selection, the SMF transfers N4signaling to the UPF that indicates the selected bearers, QoS, and otherinformation for the selected service for UE 801. The AMF transfers N2signaling to the RRC in AP 811 that indicates the selected bearers, QoS,and other information for the selected service for UE 801. The AMFtransfers N1 signaling to the RRC in UE 801. The RRC in AP 811 transfersRRC signaling to UE 801 that carries the N1 signaling and that indicatesthe selected bearers, QoS, and other information for the selectedservice for UE 801.

The RRC in UE 801 configures its SDAP, PDCP, RLC, MAC, and PHY tocommunicate with AP 811. The RRC in AP 811 configures its SDAP, PDCP,RLC, MAC, and PHY to communicate with UE 801. The SDAP in UE 801 and theSDAP in AP 811 exchange user data over their PDCPs, RLCs, MACs, andPHYs. The SDAP in AP 811 and the UPF exchange the user data over one ormore N3 links. The UPF and an external system exchange the user dataover an N6 link.

The UPF generates usage data like CDRs that characterize the user dataexchange by time, location, device, service, amount, and the like. TheUPF transfers the CDRs to the client—typically through an accountingsystem that formats and filters out the CDRs for UE 801 and transfersthem to the client in NFVI 812. The client in NFVI 812 transfers theCDRs for UE 801 to an endorser node in reference DL 822.

The endorser node in reference DL 822 executes the reference DL code inreference DL 822 to classify and rate the CDRs. The endorser node checksthe code results (accounting statement) against an endorsement rule set.The endorser node transfers a transaction endorsement back to the clientin NFVI 812. The client in NFVI 812 transfers the endorsed transactionan orderer node in reference DL 822. The orderer node transfers theendorsed transaction to the appropriate peer nodes.

The peer nodes independently execute reference DL code to classify andrate the CDRs. The peer nodes share their chain code result (accountingstatement) to form a consensus for the result. After consensus, the peernodes store the consensus result in the DL databases using a blockchainformat.

At a pre-determined number of CDRs, the chain code drives the endorsernodes and peer nodes to generate an abstract of the CDRs and transferthe CDR abstract to index DL 821. The abstract may be a significant dataredaction on individual CDRs like passing only UE ID, rough location,classification, and rate in the abstract.

A peer node in reference DL 822 transfers the CDR abstracts to anendorser node in index DL 821. The endorser node in index DL 821executes its index DL code to process the CDR abstracts. The endorsernode checks the code results (store CDR abstracts) before transferring atransaction endorsement back to the peer node in reference DL 822. Thepeer node in reference DL 822 transfers the endorsed transaction anorderer node in index DL 821. The orderer node transfers the endorsedtransaction to the appropriate peer nodes in index DL 821.

In index DL 821, the peer nodes independently execute their index DLcode to identify CDR abstract storage. The peer nodes share their coderesult (CDR abstract storage) to form a consensus for the result. Afterconsensus, the peer nodes store the CDR abstracts in the DL databasesusing a blockchain format.

At a pre-determined number of CDRs or CDR abstracts, the reference DLcode in reference DL 822 drives the endorser nodes and peer nodes togenerate a reference DL exhaustion notice. The DL exhaustion notice mayindicate another reference DL for the client. A peer node in referenceDL 822 transfers the DL exhaustion notice to an endorser node in indexDL 821. The endorser node in index DL 821 executes its index DL code toprocess the DL exhaustion notice. The endorser node checks the coderesults (new reference DL for the client in NFVI 812) beforetransferring a transaction endorsement back to the peer node inreference DL 822. The peer node in reference DL 822 transfers theendorsed transaction to an orderer node in index DL 821. The orderernode transfers the endorsed transaction to the appropriate peer nodes inindex DL 821.

In index DL 821, the peer nodes independently execute their index DLcode to identify a new reference DL for the DL client in NFVI 812. Thepeer nodes share their code result (new reference DL for the client inNFVI 812) to form a consensus for the result. After consensus, the peernodes store the result in the DL databases using a blockchain format. Apeer module in index DL 821 initiates a new reference DL and transfersthe ID for the new reference DL to DL controller 823. DL controller 823transfers the ID for the new reference DL to the client in NFVI 812. Theclient now transfers CDRs for data communication system 820 to the newreference DL.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose data communicationcircuitry to index wireless network usage data for usage analytics. Thecomputer hardware comprises processing circuitry like CPUs, DSPs, GPUs,transceivers, bus circuitry, and memory. To form these computer hardwarestructures, semiconductors like silicon or germanium are positively andnegatively doped to form transistors. The doping comprises ions likeboron or phosphorus that are embedded within the semiconductor material.The transistors and other electronic structures like capacitors andresistors are arranged and metallically connected within thesemiconductor to form devices like logic circuitry and storageregisters. The logic circuitry and storage registers are arranged toform larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose data communicationcircuitry to index wireless network usage data for usage analytics.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of presenting usage data for a wirelesscommunication network, the method comprising: index circuitry receivinga usage data request for the wireless communication network andtransferring a reference Distributed Ledger (DL) request; referencecircuitry receiving the reference DL request and transferring areference DL response indicating a reference DL Identifier (ID); theindex circuitry receiving the reference DL response and transferring ausage data response indicating the reference DL ID for the wirelesscommunication network; the reference circuitry receiving the referenceDL ID and the usage data from the wireless communication network,executing reference DL chain code, storing the usage data and lastreference block hashes in reference DL blocks, generating a usageabstraction of the usage data, and transferring the reference DL ID andthe usage abstraction; the index circuitry receiving the reference DL IDand the usage abstraction, executing index DL chain code, storing theusage abstraction, the reference DL ID, and last index block hash in anew index DL block, receiving an index data request for the wirelesscommunication network having the reference DL ID, and transferring theusage abstraction and the reference DL ID for the usage abstractionresponsive to the index data request; and the reference circuitryreceiving a reference data request having the reference DL ID and usageabstraction IDs and transferring the usage data.
 2. The method of claim1 wherein the reference circuitry receiving the usage data from thewireless communication network comprises receiving Call Detail Records(CDRs).
 3. The method of claim 1 wherein the reference circuitrygenerating the usage abstraction of the usage data comprises abstractingCall Detail Records (CDRs).
 4. The method of claim 1 wherein thereference circuitry generating and transferring the usage abstractioncomprises generating and transferring the usage abstraction responsiveto receiving a pre-determined amount of the usage data.
 5. The method ofclaim 1 wherein the reference circuitry generating and transferring theusage abstraction comprises generating and transferring the usageabstraction on a periodic time basis.
 6. The method of claim 1 whereinthe reference circuitry storing the usage data, generating the usageabstraction, and transferring the usage abstraction comprises ratingnetwork usage based on the usage data, storing the rated network usage,generating the usage abstraction of the rated network usage, andtransferring the usage abstraction of the rated network usage.
 7. Themethod of claim 1 wherein the reference circuitry storing the usagedata, generating the usage abstraction, and transferring the usageabstraction comprises classifying network usage based on the usage data,storing the classified network usage, generating the usage abstractionof the classified network usage, and transferring the usage abstractionof the classified network usage.
 8. The method of claim 1 furthercomprising: the reference circuitry transferring a reference DLexhaustion notice responsive to storing the usage data; the indexcircuitry receiving the reference DL exhaustion notice and transferringanother reference DL request; the reference circuitry receiving theother reference DL request and transferring another reference DLresponse indicating another reference DL ID; the index circuitryreceiving the other reference DL response and transferring another usagedata response indicating the other reference DL ID to the wirelesscommunication network; the reference circuitry receiving the otherreference DL ID and other usage data from the wireless communicationnetwork, executing other reference DL chain code, storing the otherusage data and other last reference block hashes in other reference DLblocks, generating another usage abstraction of the other usage data,and transferring the other reference DL ID and the other usageabstraction; the index circuitry receiving the other usage abstractionand the other reference DL ID, executing the index DL chain code,storing the other usage abstraction, the other reference DL ID, andanother index DL hash of the previous index DL block in another newindex DL block, receiving another index data request for the wirelesscommunication network, and transferring the other usage abstraction andthe other reference DL ID responsive to the other index data request;and the reference circuitry receiving another reference data requesthaving the other reference DL ID and transferring the other usage data.9. The method of claim 1 further comprising: the index circuitryreceiving another data request for the wireless communication networkand transferring another reference DL request; the reference circuitryreceiving the other reference DL request and transferring anotherreference DL response indicating another reference DL ID; the indexcircuitry receiving the other reference response and transferring otherusage data response indicating the other reference DL ID for thewireless communication network; the reference circuitry receiving theother reference DL ID and other usage data for the wirelesscommunication network, executing other reference DL chain code, storingthe other usage data and other last reference block hashes in otherreference DL blocks, generating another usage abstraction of the otherusage data, and transferring the other reference DL ID and the otherusage abstraction; the index circuitry receiving the other usageabstraction and the other reference DL ID, storing the other usageabstraction, the other reference DL ID, and another index DL hash of theprevious index DL block in another new index DL block, receiving anotherindex data request for the wireless communication network, andtransferring the other usage abstraction and the other reference DL IDresponsive to the other index data request; and the reference circuitryreceiving another reference data request having the other reference DLID and transferring the other usage data.
 10. The method of claim 1wherein the wireless communication network is divided into multiplegeographic areas and the usage data is from one of the geographic areasand further comprising the index circuitry associating the usageabstraction and the index link with the one of the geographic areas. 11.A wireless communication network comprising: index circuitry configuredto receive a usage data request for the wireless communication networkand transfer a reference Distributed Ledger (DL) request; referencecircuitry configured to receive the reference DL request and transfer areference DL response indicating a reference DL Identifier (ID); theindex circuitry configured to receive the reference DL response andtransfer a usage data response indicating the reference DL ID for thewireless communication network; the reference circuitry configured toreceive the reference DL ID and the usage data from the wirelesscommunication network, execute reference DL chain code, store the usagedata and last reference block hashes in reference DL blocks, generate ausage abstraction of the usage data, and transfer the reference DL IDand the usage abstraction; the index circuitry configured to receive thereference DL ID and the usage abstraction, execute index DL chain code,store the usage abstraction, the reference DL ID, and last index blockhash in a new index DL block, receive an index data request for thewireless communication network having the reference DL ID, and transferthe usage abstraction and the reference DL ID for the usage abstractionresponsive to the index data request; and the reference circuitryconfigured to receive a reference data request having the reference DLID and usage abstraction IDs and transfer the usage data.
 12. Thewireless communication network of claim 11 wherein the usage datacomprises Call Detail Records (CDRs).
 13. The wireless communicationnetwork of claim 11 wherein the abstraction of the usage data comprisesabstractions of Call Detail Records (CDRs).
 14. The wirelesscommunication network of claim 11 wherein the reference circuitry isconfigured to generate and transfer the usage abstraction responsive toreceiving a pre-determined amount of the usage data.
 15. The wirelesscommunication network of claim 11 wherein the reference circuitry isconfigured to generate and transfer the usage abstraction on a periodictime basis.
 16. The wireless communication network of claim 11 whereinthe reference circuitry is configured to rate network usage based on theusage data, store the rated network usage, generate the usageabstraction of the rated network usage, and transfer the usageabstraction of the rated network usage.
 17. The wireless communicationnetwork of claim 11 wherein the reference circuitry is configured toclassify network usage based on the usage data, store the classifiednetwork usage, generate the usage abstraction of the classified networkusage, and transfer the usage abstraction of the classified networkusage.
 18. The wireless communication network of claim 11 furthercomprising: the reference circuitry configured to transfer a referenceDL exhaustion notice responsive to storing the usage data; the indexcircuitry configured to receive the reference DL exhaustion notice andtransfer another reference DL request; the reference circuitryconfigured to receive the other reference DL request and transferanother reference DL response indicating another reference DL ID; theindex circuitry configured to receive the other reference DL responseand transfer another usage data response indicating the other referenceDL ID to the wireless communication network; the reference circuitryconfigured to receive the other reference DL ID and other usage datafrom the wireless communication network, execute other reference DLchain code, store the other usage data and other last reference blockhashes in other reference DL blocks, generate another usage abstractionof the other usage data, and transfer the other reference DL ID and theother usage abstraction; the index circuitry configured to receive theother usage abstraction and the other reference DL ID, execute the indexDL chain code, store the other usage abstraction, the other reference DLID, and another index DL hash of the previous index DL block in anothernew index DL block, receive another index data request for the wirelesscommunication network, and transfer the other usage abstraction and theother reference DL ID responsive to the other index data request; andthe reference circuitry configured to receive another reference datarequest having the other reference DL ID and transfer the other usagedata.
 19. The wireless communication network of claim 11 furthercomprising: the index circuitry configured to receive another datarequest for the wireless communication network and transfer anotherreference DL request; the reference circuitry configured to receive theother reference DL request and transfer another reference DL responseindicating another reference DL ID; the index circuitry configured toreceive the other reference response and transfer other usage dataresponse indicating the other reference DL ID for the wirelesscommunication network; the reference circuitry configured to receive theother reference DL ID and other usage data for the wirelesscommunication network, execute other reference DL chain code, store theother usage data and other last reference block hashes in otherreference DL blocks, generate another usage abstraction of the otherusage data, and transfer the other reference DL ID and the other usageabstraction; the index circuitry configured to receive the other usageabstraction and the other reference DL ID, store the other usageabstraction, the other reference DL ID, and another index DL hash of theprevious index DL block in another new index DL block, receive anotherindex data request for the wireless communication network, and transferthe other usage abstraction and the other reference DL ID responsive tothe other index data request; and the reference circuitry configured toreceive another reference data request having the other reference DL IDand transfer the other usage data.
 20. The wireless communicationnetwork of claim 11 wherein the wireless communication network isdivided into multiple geographic areas and the usage data is from one ofthe geographic areas and further comprising the index circuitryconfigured to associate the usage abstraction and the reference DL IDwith the one of the geographic areas.